These options are designed to deal with cases where the target file may not be exactly the same as any of the old files that the update was built for. If you use these options, UpdateMaker will associate them with the type of file involved and will recall them the next time you choose the same type of file in the build specifications.
You need to be familiar with the structure of Macintosh files to use these options.
If you are not familiar with the various types of resources and their properties, it would be best to leave these controls on their default settings.
Each option allows you to specify particular behaviour for the data fork and for a list of resources. The resources must be specified as a type followed by an ID, an ID range (separated by blanks or commas, but not the “-” sign), or “all”. For example:
CODE 12
DITL 128
Spam –9,–1
FONT ALL
UpdateMaker will display an alert message if it doesn’t understand a line and will select the offending text for correction.
The Always–Replace List
Resources named in this list are always completely replaced when updating. UpdateMaker will insert a copy of the resources as they appear in the “new” file into the update document. When updating it will use them to construct the updated file and ignore any such resources in the update target. This is useful if you know that the resources may have been changed by the user in the update target and you wish to override those changes. It is also a safe option because the updated file will still be identical to the “new” file that was used to make the update.
SIZE 0 resources in applications are a common example of where this option is needed. Because they are added or changed in applications by the Finder when the user adjusts the preferred memory size, many users will have different SIZE 0’s. UpdateMaker therefore automatically inserts SIZE 0 into the replace list. You may delete it or move it to another list if you wish.
The Always–Copy (required) List
Resources named in this list are always copied from the update target when updating, without checking in any way that they correspond to those resources in the new file when the update was built. This is more dangerous, in that it will not necessarily generate a file that is identical to the original “new” file.
For example, if you knew that the SIZE 0 resources in the update targets would always be present, and you wished to preserve the users preferred memory size, you could move the SIZE 0 specification into this list.
The Always–Copy (if present) List
Resources named in this list are copied from the update target when updating, just as above. The difference is that UpdateMaker does not require them to be present. For example, if you wished to update a file in which you knew that the users might have placed any number of ‘Spam’ resources with ID’s between 1 and 1000, and you wanted to preserve those resources in the updated version, this would be the appropriate option.
In this list you may optionally use only a type specification without an ID or a range which will be accepted as meaning all resources of that type.
